Method and system for controlling functionality of lighting devices from a portable electronic device

ABSTRACT

Systems and methods for controlling lighting devices are disclosed. The system includes a processor in communication with a portable electronic device. The method includes, by the processor, receiving geolocation data corresponding to an electronic device, and identifying one or more light-enabled facilities that are within a distance range of the electronic device. Each of the light-enabled facilities comprises a controller that is communicatively coupled to one or more lighting devices in a network of lighting devices. The method further includes receiving a light operation request comprising a selected one of the light-enabled facilities and a scene from the electronic device, and transmitting the light operation request to cause the controller to activate at least one lighting device at the selected light-enabled facility according to the scene to the controller at the selected light-enabled facility.

RELATED APPLICATIONS AND CLAIMS OF PRIORITY

This patent application is a continuation of and claims priority to U.S. patent application Ser. No. 16/154,050, filed Oct. 8, 2018, now U.S. Pat. No. 10,492,266, issued Nov. 26, 2019, which is a continuation of U.S. patent application Ser. No. 15/786,274, filed Oct. 17, 2017, now U.S. Pat. No. 10,098,201, issued Oct. 9, 2018. The disclosures of all such priority applications are fully incorporated into this document by reference.

BACKGROUND

This disclosure is related to a method and system for controlling functionality of light devices and in particular to a method and system for controlling light devices from a portable electronic device.

Modern lighting systems include many features that were not previously available to facility operators and users. For example, lighting systems that include light emitting diode (LED) luminaires or other types of luminaires may offer features such as: controllable dimming; color selection and color tuning; adjustment of other characteristics of emitted light such as color temperature or D_(uv); control of the shape and/or direction of emitted light beams; and pre-programmed scenes or customized scenes that incorporate a set of pre-programmed features.

In facilities such as theaters, concert venues, sports fields and stadiums, and even in commercial buildings, the lighting needs can change frequently depending on who is using the facility at any given time. For example, a venue may be used for a convention or business meeting during the day and a concert or social event in the evening. A sports field may be used for a football or soccer game at one time of day and a lacrosse team practice at another time of day. However, lighting systems do not easily adapt to the needs of each user and event. Instead, lighting systems are typically set in a “fully on” or “fully off” arrangement unless the facility is staffed with technicians who can manually change the lighting system scenarios in response to new users' needs.

This disclosure describes methods and systems for controlling the functionality of a network of one or more lighting devices.

SUMMARY

A system for controlling one or more lighting devices in a lighting device control system includes a processor in communication with a portable electronic device and a non-transitory memory device. The non-transitory memory device contains programming instructions for a lighting system control application. The system receives geolocation data corresponding to an electronic device and identifies one or more light-enabled facilities that are within a distance range of the electronic device. Each of the light-enabled facilities may include a controller that is communicatively coupled to one or more lighting devices in a network of lighting devices. The system also receives a light operation request comprising a selected one of the light-enabled facilities and a scene from the electronic device, and transmit, to the controller at the selected light-enabled facility, the light operation request to cause the controller to activate at least one lighting device at the selected light-enabled facility according to the scene.

In certain embodiments, the light operation request may also include a service time duration, and the light operation request may cause the system to maintain the at least one lighting device in an activated state according to the scene until occurrence of an expiration event. Optionally, the expiration event may be occurrence of an off-time corresponding to the at least one lighting device or the selected light-enabled facility and/or end of the service time duration. In an embodiment, the light operation request is configured to, when received by the controller, cause the controller to initiate or maintain the at least one lighting device in a first condition at a first time, and then switch the at least one lighting device to a second condition when the time duration expires.

Before transmitting the set of available scenes for the one or more controllers to the portable device, the system may receive from the portable electronic device, an identifier associated with one of the one or more controllers, and may then transmit to the portable electronic device a set of available scenes for the controller associated with the receiver identifier.

In some embodiments, the system may receive an identifier associated with the controller from the electronic device, and transmit to the electronic device a set of available scenes for the controller.

In some embodiments, the system may determine whether the electronic device is authorized to cause the controller to implement the light operation request by receiving a user credential from the electronic device or the controller, and verifying the user credential.

Alternatively and/or additionally, the system may determine whether the electronic device is authorized to cause the controller to implement the light operation request by receiving a first account identifier from the controller associated with the selected scene, receiving a second account identifier from the electronic device, determining user credentials by comparing the first account identifier with the second account identifier, and verifying the user credential information.

In at least one embodiments, the system may identify one or more light-enabled facilities by using geolocation data to identify a location of the electronic device, and accessing a database of light-enabled facilities and identify, from data in the database, one or more of the light-enabled facilities having a location that is within the distance range of the identified location of the electronic device.

In some embodiments, the system may, before receiving the light operation request, retrieve one or more lighting service schedules for the identified one or more light-enabled facilities, and transmit the one or more lighting service schedules to the electronic device.

In one or more embodiments, the system may use user account information associated within the electronic device to authenticate the light operation request, and may transmit the light authorization request to the controller only after authenticating the light operation request.

Optionally, a controller at the selected light-enabled facility may be configured to detect whether the electronic device or another device that is associated with an account of a user of the electronic device is in proximity of the selected light-enabled facility, and only initiate the scene at the selected light-enabled facility of the electronic device or the other device is in proximity of the selected light-enabled facility.

In some embodiments, each of the one or more scenes may include a set of data corresponding to one or more optical characteristics of one or more lighting devices in the network. The one or more optical characteristics may include a brightness or dimming level, color temperature, color, D_(uv), beam shape, and/or beam direction.

In at least one embodiment, before transmitting the set of available scenes for the one or more controllers to the portable electronic device, the system may receive, from at least one of the one or more controllers, an indication that the portable electronic device has paired with the at least one controller.

In some embodiments, the system may also detect geolocation data indicating a location of the portable electronic device, identify a group of the light-enabled facilities that are within a distance range from the location of the portable electronic device, transmit identifying information for the group of the light-enabled facilities to the portable electronic device, and receive a selection of one of the local light-enabled facilities to which to direct the light operation request from the portable electronic device. Transmitting the set of available scenes for one or more controllers may include transmitting the set of available scenes associated with one or more controllers of the selected local light-enabled facility. Optionally, the system may also include a database of data for a plurality of light-enabled facilities, and the system may identify the group of light-enabled facilities that are within a distance range from the portable electronic device by accessing the database and extracting identification data for light-enabled facilities having location data that is within the distance range of the location of the portable electronic device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a network of lighting devices, with a proximate mobile electronic device and gateway controller that are used to control the light emitted by the network of devices.

FIG. 2 illustrates an example of a lighting device that may be used with a network of lighting devices.

FIG. 3 illustrates example steps that a gateway controller may take when being used to control a lighting device.

FIGS. 4a and 4b illustrate example components of a gateway controller and one or more fixture controllers of a lighting device.

FIG. 5 illustrates example steps that a portable electronic device may take when being used to control a lighting device.

FIG. 6 illustrates an example of a portable electronic device user interface that may be used to control the light emitted by one or more lighting devices.

FIG. 7 illustrates example steps that a portable electronic device may take when being used to control a lighting device.

FIG. 8 illustrates an example user interface by which a user may schedule lighting service at any of a plurality of facilities in a geographic region.

FIG. 9 illustrates example steps by which a system may control lighting services at multiple light-enable facilities.

FIG. 10 illustrates various hardware components that may be included in one or more electronic devices.

DETAILED DESCRIPTION

As used in this document, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise. Unless defined otherwise, all technical and scientific terms used herein have the same meanings as commonly understood by one of ordinary skill in the art. In this document, when terms such “first” and “second” are used to modify a noun, such use is simply intended to distinguish one item from another, and is not intended to require a sequential order unless specifically stated. As used in this document, the term “comprising” (or “comprises”) means “including (or includes), but not limited to.”

In this document, the terms “lighting device,” “light fixture,” “luminaire” and “illumination device” are used interchangeably to refer to a device that includes a source of optical radiation. Sources of optical radiation may include, for example, light emitting diodes (LEDs), light bulbs, ultraviolet light or infrared sources, or other sources of optical radiation. In the embodiments disclosed in this document, the optical radiation emitted by the lighting devices includes visible light. A lighting device will also include a housing, one or more electrical components for conveying power from a power supply to the device's optical radiation source, and optionally control circuitry.

In this document, the terms “communication link” and “communication path” mean a wired or wireless path via which a first device sends communication signals to and/or receives communication signals from one or more other devices. Devices are “communicatively connected” if the devices are able to send and/or receive data via a communication link. “Electronic communication” refers to the transmission of data via one or more signals between two or more electronic devices, whether through a wired or wireless network, and whether directly or indirectly via one or more intermediary devices.

A “communication interface” of a gateway controller or other electronic device is a hardware element configured to enable the device to transmit and/or receive data signals from proximate devices and/or a communication network. Communication interfaces for communicating with proximate devices may include, for example, a short range wireless communication interface such as a transmitter, a near field communication (NFC) or radio frequency identifier (RFID) tag, or a Bluetooth™ or Bluetooth™ Low Energy (BLE) transceiver. Communication interfaces for indirectly communicating with proximate or non-proximate devices via one or more communication networks may include, for example, a wireless network card with wireless network antenna, a data port, or the like.

In this document, the terms “controller” and “controller device” mean an electronic device or system of devices configured to command or otherwise manage the operation of one or more other devices. For example, a fixture controller is a controller configured to manage the operation of one or more light fixtures to which the fixture controller is communicatively linked. A controller will typically include a processing device, and it will also include or have access to a memory device that contains programming instructions configured to cause the controller's processor to manage operation of the connected device or devices.

In this document, the terms “memory” and “memory device” each refer to a non-transitory device on which computer-readable data, programming instructions or both are stored. Except where specifically stated otherwise, the terms “memory” and “memory device” are intended to include single-device embodiments, embodiments in which multiple memory devices together or collectively store a set of data or instructions, as well as one or more individual sectors within such devices.

In this document, the terms “processor” and “processing device” refer to a hardware component of an electronic device (such as a controller) that is configured to execute programming instructions. Except where specifically stated otherwise, the singular term “processor” or “processing device” is intended to include both single processing device embodiments and embodiments in which multiple processing devices together or collectively perform a process.

A “computing device” or “electronic device” refers to an electronic device having a processor, a memory device, and a communication interface for communicating with proximate and/or local devices. The memory will contain or receive programming instructions that, when executed by the processor, will cause the electronic device to perform one or more operations according to the programming instructions. Examples of electronic devices include personal computers, servers, mainframes, virtual machines, containers, gaming systems, televisions, and portable electronic devices such as smartphones, wearable virtual reality devices, Internet-connected wearables such as smart watches and smart eyewear, personal digital assistants, tablet computers, laptop computers, media players and the like. Electronic devices also may include appliances and other devices that can communicate in an Internet-of-things arrangement, such as smart thermostats, home controller devices, voice-activated digital home assistants, connected light bulbs and other devices. In a client-server arrangement, the client device and the server are electronic devices, in which the server contains instructions and/or data that the client device accesses via one or more communications links in one or more communications networks. In a virtual machine arrangement, a server may be an electronic device, and each virtual machine or container may also be considered to be an electronic device. In the discussion below, a client device, server device, virtual machine or container may be referred to simply as a “device” for brevity. Additional elements that may be included in electronic devices will be discussed below in the context of FIG. 8.

FIG. 1 illustrates a lighting system in which any number of lighting devices 101, 102 are positioned at various locations in an environment, such as a wall, ceiling, mast, tower or other supporting structure in a stadium, arena, concert hall, outdoor amphitheater, park or other sports or entertainment facility, or a commercial building or other light-enabled facility. The lighting system also includes a gateway controller 104 communicatively coupled to one or more fixture controllers 111, 112 that are connected to one or more lighting devices 101, 102. Gateway controller 104 is configured to pair with a portable electronic device 103, receive a light operation request from the portable electronic device 103 and control at least one lighting device 101, 102 via the fixture controller 111, 112 according to the light operation request. Each of the gateway controller 104 and portable electronic device 103 may be capable of communicating with a communication network 105, such as a cellular communication work, an Internet, a mesh network or other wired or wireless communication networks. The fixture controller 111, 112 includes various components of an illumination device's control circuitry.

A remote server 106 also may be communicatively connected to the communication network 105 so that it can communicate with the portable electronic device, gateway controller, and/or fixture controllers. The remote server 106 may include or be connected one or more memory devices that collectively store a database 108 of data for multiple light-enabled facilities, such as scheduling data, data about available lighting devices and optional functions, available scenes, costs of various services and other data. The portable electronic device 103 may include a memory device containing programming instructions that are configured to cause the portable electronic device to perform various functions. In addition, or alternatively, the portable electronic device 103 may access the remote server 106 via a communication network 105 to obtain programming instructions that are stored on and received from and/or executed by the remote server.

Referring to FIG. 2, an example lighting device 101 includes an optical radiation source, such as any number of lighting modules that include LEDs, and in various embodiments a number of LED modules sufficient to provide a high intensity LED device. In various embodiments, a lighting device may include multiple types of LED modules. For example, a lighting device may include a first type of LED module 203 having LEDs that are configured to selectably emit white light of various color temperatures, along with a second type of LED module 205 having LEDs that are configured to selectably emit light of various colors. The lighting device 101 may include a housing 201 that holds electrical components such as a fixture controller, a power source, and wiring and circuitry to supply power and/or control signals to the LED modules. A fixture controller may also be an external device to the lighting device.

In FIGS. 4a and 4b , example components of a gateway controller 401 and one or more fixture controllers 431 a, . . . 431 n are shown. In this document, the term “gateway controller” refers to a central controller device that receives commands from a remote electronic device and routes the commands to appropriate lighting device fixture controllers in a network of lighting devices. The gateway controller 401 may include a processor 403 and a communications interface that includes a router or switch 402 with one or more Ethernet ports or optical fiber connectors configured to receive an Ethernet and/or fiber-optic cable. Other types of cables and connectors may be used, but for purposes of this disclosure Ethernet and fiber-optic cables and connectors will be used as examples.

Each fixture controller 431 n also includes a processor 433 n and, in wired connection embodiments, a switch 432 n having at least two ports that are each configured to receive an Ethernet or fiber-optic cable. With the ports described above as start and end points, the gateway controller 401 is connected via a communication link 411, such as an Ethernet or fiber-optic cable, to form a connection to at least one of the fixture controllers 431 a. Alternatively, and/or additionally, the communication link 411 may also be a wireless communication link such as a Wi-Fi, a Bluetooth, a NFC network, a mesh network or other communication links.

Optionally, each fixture controller may be directly communicatively connected to the gateway controller 401. Each fixture controller (e.g., 431 a) may also be similarly connected to at least one other fixture controller (e.g., 431 b) via a serial communication link 412, 413 (in this embodiment, an Ethernet or fiber-optic cable) in a daisy chain configuration. In this way, the first fixture controller 431 a in the chain may be connected to the gateway controller 401 and a next fixture controller according to a ring topology. The next fixture controller 431 b may be connected to the previous fixture controller 431 a and a next fixture controller in the chain until a final fixture controller 431 n is reached. The final fixture controller 431 n also may be connected to the gateway controller via a serial communication link 416. In this way, the gateway controller 401 may send commands to each of the lighting device's fixture controllers via the various communication links, and the gateway controller 401 may receive data from each of the lighting device's fixture controllers via the various communication links. In some embodiments, communication may be in a single direction around the loop formed by the devices and communication links; in other embodiments communication may be bidirectional in both the clockwise and counterclockwise directions around the communication links. The ring topology shown in FIGS. 4a and 4b is optional, and other configurations such as a hub-and-spoke configuration (in which the gateway controller is the hub) or a mesh network may be used.

Any of the lighting device fixture controllers (e.g., 431 n) may be connected to one or more external devices 451, such as a camera or computing device. This connection may be via a wired connection through an Ethernet or other type of switch 432 n as shown in FIG. 4b , or it may be a wireless connection via a wireless receiver such as a Wi-Fi receiver 434 n or a short-range communication receiver 435 n such as a receiver configured to receive signals via a Bluetooth™ Low Energy or other communications protocol.

As noted above, the gateway controller 401 also may be communicatively connected to the remote server (106 in FIG. 1) and portable electronic devices (103 in FIG. 1) via one or more communication interfaces to networks such as a fiber optic network 441, and/or a wireless communication network such as a local area network, cellular network and/or the Internet.

Each lighting device will have an associated address, such as an Internet Protocol address. When sending control data to the lighting devices, the gateway controller may designate the data to be used by all devices, by a group of the devices, or by individual devices. As each device receives data, its fixture controller may examine the data to determine whether that data is intended for it. Alternatively, a gateway controller may be configured to be in a “pass-through” mode where it will forward any received data directly to lighting devices for any further processing. One way in which this may be done is that the gateway controller may associate one or more device addresses with each set of data. For example, the gateway controller may send a start data signal, one or more device addresses, and a control data set. If a device detects (based on the device address that follows the start signal) that a data set is intended for that device, it may receive and apply that data until the stop command is received. Each device will also pass the data along to the next interconnected device in the network via the Ethernet or fiber-optic cable.

Optionally, one or more of the lighting devices may add data to the data stream before passing the data stream along to a next device. For example, any lighting device's fixture controller 431 b may receive data from one or more external or internal sensors, as described above. The fixture controller may append its device's address to the data stream, so that the data is passed through all lighting devices in the chain and the fixture controller of the final device 431 n in the chain will pass the data on to the gateway controller 401.

When an external device 451 (such as a camera) is connected to any lighting device's Ethernet switch, the external device also may have an associated address, and the gateway controller 401 may send data to the external device using the external device's address and the wired network described above. Similarly, the fixture controller 431 n to which any external device 451 is attached may send data from the external device to the gateway controller 401 via the data stream just as it may do with any other data as described above.

Several of the communication links shown in FIGS. 4a and 4b are labeled with communication protocols that may be used to transmit data across the links. Those labels are by way of example only; other communication protocols may be used with any or all of the links shown. In addition, in various embodiments, the gateway controller 401 may include programming configured to translate control data received from a first protocol into a second protocol that is compatible with the lighting devices to which the gateway controller will send commands. In this way, the gateway controller 401 serves as a universal protocol gateway between the lighting devices and one or more external devices or systems. For example, the gateway controller 401 may translate data received from the portable electronic device in a NFC communication protocol or other wireless protocol (such as Bluetooth™ Low Energy), whereas the gateway controller 401 may communicate with the remote server (106 in FIG. 1) in an Ethernet protocol, and/or it may translate data received and/or it may translate data received in a fiber channel protocol, and/or it may translate data that it receives via other protocols, into a communication protocol that is compatible with that of the illumination devices, such as I²C or that described in the American National Standards Institute (“ANSI”) “Entertainment Technology—USITT DMX512-A—Asynchronous Serial Digital Data Transmission Standard for Controlling Lighting Equipment and Accessories”, which is commonly referred to a DMX512 or simply DMX. This document will use the term “DMX” to refer to the DMX512 standard, and its various variations, revisions and replacements, including any future revisions or replacements that may be consistent with the processes described in this disclosure.

Returning to FIG. 1, gateway controller 104 may communicate with a proximate portable electronic device 103 via a direct or indirect communication link. The gateway controller 104 may communicate with one or more fixture controllers 111, 112 or any number of fixture controllers, each connecting to one or more lighting devices 101, 102. The gateway controller 104 as well as the proximate portable electronic device 103 may communicate with the remote server 106 by any number of communication links. The remote server 106 may be a cloud-based server that communicates with the other devices via the communication network 105.

FIG. 3 is a flow diagram illustrating a method of controlling one or more lighting devices in a system such as that disclosed above. The gateway controller may detect 301 that a portable electronic device on which a lighting control application is installed is proximate to the lighting device. Devices are “proximate” to each other if they are within a communication range of each other on a local area network or using a short-range communication or NFC communication protocol.

Short-range communication transceivers are devices that directly communicate with each other via relatively short distances on the order of 100 meters or less, or 10 meters or less. Examples of short-range transceivers include those that adhere to short-range communication protocols such as ZigBee®, Bluetooth®, and Bluetooth® Low Energy (BLE) transceivers, and/or via infrared (IR) light transceivers. NFC transceivers are ultra-short range transceivers that adhere to one or more standards for radio frequency communications that may be used when two devices are in close proximity, and may include hardware elements such as loop antennas that exchange information via electromagnetic induction. Protocols for implementation of NFC may comply with industry standards such as ISO/IEC 18092 or ISO/IEC 18000-3, published by the International Standards Organization. Typical ranges for near field communications are approximately 10 cm or less, although it may be 20 cm or less, 4 cm or less, or other ranges. By receiving a connection request via a short-range communication protocol or NFC protocol, the gateway controller will thus detect that the mobile electronic device is proximate to the lighting device.

Detection 301 of proximity may occur, for example, by receiving a connection request from the portable electronic device via a short-range communication or NFC transceiver. Alternatively, the detection 301 may occur by receiving a connection request from the portable electronic device via a known wireless local area network (WLAN), such as a Wi-Fi network that has a limited range and to which the lighting device is also communicatively connected. By receiving a connection request from a mobile electronic device that is communicatively connected to the same WLAN to which the gateway controller is connected, the gateway controller will thus detect that the mobile electronic device is proximate to the gateway controller.

The gateway controller will also receive, via the communication interface, a light operation request 302 from the portable electronic device. The communication may occur directly from the portable electronic device via short-range or NFC communication, or indirectly such as via the remote server and one or more networks. The light operation request will be one or more data packets that include one or more settings for one or more optical characteristics of light that the optical radiation source of the lighting device and/or other communicatively connected lighting devices may emit. The one or more optical characteristics comprise may include settings such as a brightness or dimming level, color temperature, color, D_(uv), beam shape, and/or beam direction of the light emitted by the optical radiation source.

The gateway controller may determine whether the portable electronic device is authorized to cause the gateway controller to implement the light operation request 303. If the gateway controller determines that the portable electronic device is authorized to initiate the light operation request, it will activate one or more lighting devices by causing the optical radiation source of each lighting device to emit light that exhibits the one or more optical characteristics of the light operation request 304. If the gateway controller determines that the portable electronic device is not authorized to initiate the light operation request, it will not implement the request and thus not activate the optical radiation source according to the request 305.

To determine whether the portable electronic device is authorized to cause the gateway controller to implement the light operation request 303, the gateway controller may determine whether the portable electronic device is associated with a valid unlock token for the light operation request. A valid unlock token is a digital identifier that the gateway controller knows represents authorization to activate or change one or more characteristics of emitted light, such as a code or authentication token. The gateway controller may receive the unlock token from the portable electronic device with the light operation request and compare the token with a set of locally or remotely stored authentication tokens to determine whether the received token matches a known valid token or adheres to a valid token standard. Alternatively, the gateway controller may receive an account identifier for the portable electronic device, transmit the account identifier to a remote server so that the remote server can perform the authentication, and receive the unlock token from the remote server if the remote server determines that the portable electronic device is authorized to initiate the light operation request. Alternatively, if the light authorization request is sent to the gateway controller from a remote server, the remote server may send the unlock token to the gateway controller.

Upon determining that the portable electronic device is authorized to submit the light operation request, the gateway controller may activate one or more lighting devices according to the selected the one or more optical characteristics in the light operation request 304. For example, the gateway controller may send command(s) to the one or more lighting devices to cause each lighting device's optical radiation source to emit light that exhibits the optical characteristics values of the light operation request. The fixture controller associated with each lighting device will implement one or more commands to control operation of the optical radiation source.

Example methods for altering optical characteristics of LED lights are disclosed in, for example: (i) U.S. Pat. No. 9,188,307 to Casper et al., titled “High Intensity LED Illumination Device with Automated Sensor-Based Control”; (ii) U.S. Pat. No. 9,189,996 to Casper et al., titled “Selectable, Zone-Based Control for High Intensity LED Illumination System”; (iii) U.S. patent application Ser. No. 15/670,659, filed by Nolan et al. and titled “Lighting Device LED Module with Effects for Color Temperature Tuning and Color Tuning”; and (iv) U.S. patent application Ser. No. 15/670,671, filed by Nolan et al. and titled “Lighting Device LED Module with Effects for Beam Spread Tuning and Beam Shaping.” The disclosures of each of these patents and patent applications are fully incorporated into this document by reference.

The optical characteristics may include a scene, which is a set of data corresponding to lighting device settings that will yield various optical characteristics of the emitted light for a group of networked lighting devices. For example, a scene may correspond to a type of a sport, such as football, soccer, basketball, tennis, table tennis or any other sports. A scene may also correspond to a type of event, such as a dance party, a birthday party, a lecture, a game or a social event. Each scene may include a set of data corresponding to one or more optical characteristics of at least one of the networked lighting devices. For example, a scene for playing football in a football field may include data that corresponds to full illuminance setting for all of the lights around the football field. In another example, a scene for ice skating in an arena may include data that correspond to certain lights at full illuminance and certain light at a dimmed level. Alternative scenes for the arena may include scenes for a basketball game or music concert. In another example, a scene for a lecture in a lecture hall may include data that correspond to a spotlight above the podium at full illuminance and other lights in the lecture hall at a dimmed level. In another hall, available scenes for a gymnasium may include options for: (i) a game scene in which all lights in the gym are illuminated at their highest level; (ii) a practice scene in which only lights directed to the court are lighted at a full illuminance level while lights directed to spectator areas are operated at a reduced illuminance level (i.e., dimmed); and (iii) a half-court scene in which lights directed to a first half of the court are operated full illuminance while lights directed to the second half of the court are operated at a lesser illuminance level. Optionally, a scene may include some setting values will change over time. If so, then the scene may include instructions for the gateway controller to cause the values of those optical characteristics of the emitted light to change over time according to the scene.

Optionally, the light operation request may include a time duration. The time duration is a data point indicative of a numeric start time, stop time and/or or a duration for activation of one or more characteristics of the optical radiation source. If so, then when activating one or more lighting devices according to the selected scene and the time duration, the gateway controller will initiate or maintain the optical radiation source of the lighting devices in a first condition (such as “on”) according to the selected characteristics at a first time, via the fixture controller associated with each lighting device. Then when a time out condition occurs 306 corresponding to expiration (i.e., the off time or the end of the duration), the gateway controller will cause the lighting devices to transition to a second operating condition by deactivating the optical radiation source and/or the selected characteristics 309. Deactivation may include, via the fixture controller associated with each lighting device, completely turning the light off, or returning the light to a default setting that does not include all of the selected characteristic values of the light operation request. Optionally, the gateway controller may receive an extension request 307 from the mobile electronic device before the time expires. The extension request will include a new (and later) stop time or an extension to the duration. If the gateway controller determines that the mobile electronic device is authorized to extend the time of operation according to the extension request (using authorization procedures such as those described above), the gateway controller will continue to activate the optical radiation source 308 with the requested characteristic values until the extended time expires, at which time the fixture controller will deactivate the light as described above.

Now, with reference to FIG. 5, an example of a diagram of a process in the portable electronic device and/or other components of the system is further explained. A portable electronic device may include a processor and a display having a user interface. The portable electronic device may include or have access to a non-transitory computer readable medium containing the programming instructions. The programming instructions, when executed, may cause the processor to: pair (and/or detect that the portable electronic device has paired) with a gateway controller in proximity to the portable electronic device 501; identify one or more scenes 502; cause the user interface to display the one or more scenes 503; receive, via the user interface, a user selection of a scene from the one or more scenes and a desired time duration 504; generate or otherwise identify a light operation request comprising the selected scene and the time duration 505; and transmit the light operation request to the gateway controller to cause the gateway controller to activate at least one of the one or more lighting devices according to the selected scene and the desired time duration 506.

In identifying the one or more scenes 502, in some scenarios, the portable electronic device may receive the scenes from the gateway controller after pairing with the gateway controller. For example, each gateway controller may store one or more available scenes that correspond to a type of sport or event suitable for the lighting devices that are installed at the premises where the gateway controller is installed and controlled by the gateway controller. Upon pairing with a proximate gateway controller, a portable electronic device may receive data about the available scenes from the gateway controller and display these scenes on its display for user selection. Alternatively, upon pairing with a gateway controller, the portable electronic device may transmit an identifier of the gateway controller to a remote server, which may responsively return a set of available scenes for the identified gateway controller. In another alternative embodiment (explained in more detail below in FIG. 8) the portable electronic device may receive, from a remote server, available scenes for multiple gateway controllers located in a geographic area.

As illustrated above, the gateway controller may first determine whether the portable electronic device is authorized to initiate the light operation request before activating one or more lighting devices according to the selected scene and the time duration. Upon determining the light operation request has been authorized, the gateway controller may transmit a message indicating such authorization to the portable electronic device. Correspondingly, the portable electronic device may be configured to receive a message from the gateway controller and cause the user interface to output a confirmation message indicating that the light operation request has been authorized 507.

To determine whether a light operation request is authorized, in some scenarios, the gateway controller may determine whether the portable electronic device has provided valid user credential information, such as user account identification information and/or user password. The portable electronic device may transmit such user credential information to the gateway controller, which in turn transmits the same credential information to the remote server for authorization.

Alternatively, the portable electronic device may directly communicate with the remote server and transmit the user credential to the remote server via an encrypted connection, such as the secure sockets layer (SSL) protocol, in which case the remote server may signal to the gateway controller or the remote electronic device that the light authorization request is authorized. In addition, the portable electronic device may also include the account identifier associated with the portable electronic device in the user credential data.

If the authorization is given to the gateway controller by the remote sever or portable electronic device, then the gateway controller may wait to receive the authorization before the gateway controller will send commands to cause any of its networked lighting devices to implement the light operation request. If the authorization is given to the portable electronic device controller by the remote sever or the gateway controller, then the portable electronic device may wait to receive the authorization before it will send the light operation request to the gateway device.

In a non-limiting example, a remote server may be configured to receive the credential data from the portable electronic device, where the credential data includes the account identifier. When a gateway controller communicates with the remote server to request authorization of a light operation request from a portable electronic device, the gateway controller transmits data in the light operation request and the account identifier associated with the portable electronic device that initiated the light operation request. Upon receiving the light operation request and account identifier from the gateway controller, the remote server compares the account identifier it received from the gateway controller with the account identifier received from the portable electronic device directly, to determine the corresponding user credential information associated with the account identifier. Then the remote server uses the user credential information to determine whether the light operation request is authorized. Upon determining that the light operation request is authorized, the remote server may transmit to the gateway controller a confirmation message indicating that the portable electronic device is authorized to initiate the light operation request. Subsequently, the gateway controller may transmit the confirmation message to the portable electronic device.

Optionally, a light operation request may include a command to operate a single lighting device, multiple lighting devices, or all lighting devices in a system that is communicatively connected to the gateway controller. For example, the light operation request may include one or more settings for one or more optical characteristics of light that a first lighting device may emit and different settings for optical characteristics of light emitted by a second lighting device. To do this, the light operation request may include an identifier for each lighting device to which commands will be directed, such as an address of the lighting device, or it may include a general command such as “apply the light operation request to all connected lighting devices.”

FIG. 6 illustrates an example portable electronic device 601 with user interface 602. The user interface 602 may be a touch-sensitive display device. In other embodiments, instead of or in addition to the display the user interface may include other user input/output hardware such as a microphone and/or audio speaker, a keyboard or keypad, or another user interface device. The user interface 602 may include a fixture selector 603 via which the user may select one or more lighting devices to control, and a time selector 604 via which a user may enter a time duration 614 that may include a start time, stop time or duration. (Alternatively, the system may identify a default time duration, which may be part of a scene or part of other programming instructions.) The user interface 602 also may include any number of lighting characteristics selectors 605, 606 via which the user may enter values for one or more user-selectable settings for characteristics of the light to be emitted by the selected lighting device(s). The system may display various candidate user-selectable settings 615, such as a data entry field, a list of options or another selector, for characteristics that the user is authorized to select. For any settings that are locked for the user's account (i.e., not yet unlocked because the user is not yet authorized to implement the settings), the user-selectable settings 616 may be displayed in a non-selectable format, such as a shield or overlay, or in a greyscale or other format that is not actuatable by the user until the user unlocks the setting. The user interface also may include an actuator 621 via which the user may unlock the setting, such as a purchasing interface by which a user may purchase access to the relevant feature.

Optionally, the user interface may include a scene selector 607 via which the user may select a scene that includes a set of one or more characteristics for one or more lights, in which the setting value for at least some of the characteristic(s) will change over time. The available values 617 may include pre-defined scenes, or the system may provide a scene creator user interface via which the user may select the settings, lighting devices and times that will define a new scene or adjust a pre-defined scene.

FIG. 7 illustrates a process that a portable electronic device may follow to initiate a light operation request for one or more proximate lighting devices. The portable electronic device may include a user interface that outputs various candidate optical characteristics for the optical radiation source 701. For at least some of the candidate optical characteristics, the user interface may also display user-selectable settings. The system also may output lock/unlock (as discussed in FIG. 6) status indicia 702 of whether an account associated with portable electronic device or its user has unlocked the ability to select settings for each characteristic. For example, for characteristics that are not locked, user-selectable settings may be presented in a user-selectable format, such as a data entry field, list, or other structure. Characteristics for which user-selectable settings that are locked will not be displayed in a user-selectable format, and may be displayed in grayscale, in shielded format, or with other indicia showing that they are locked, or they may not be displayed at all.

For any characteristic that is locked, the user may input (and the portable electronic device may receive via the user interface) an unlock request 703 and transmit the unlock request to the gateway controller. If so, the gateway controller may generate and transmit to a remote server a command to charge a user's account an amount required to unlock the setting 705. Upon receiving confirmation from the remote server that the account has been charged, the gateway controller may send to the portable electronic device an unlock code, e.g., an unlock token, to unlock 705 the characteristic so that the user can select the value of that characteristic's setting. Alternatively, and/or additionally, the portable electronic device may directly send the unlock request to the remote server and receive an unlock code from the remote server.

When the portable electronic device receives, via the user interface, a selection of at least one of the candidate optical characteristics and a value for an associated setting for each selected optical characteristic 711, it will generate a light operation request 712 as data comprising each of the one or more selected optical characteristics and its associated setting's value and an account identifier. The portable electronic device will then transmit 713 the light operation request to the gateway controller via an NFC or short range communication protocol.

FIG. 8 illustrates a user interface 801 that may be used to schedule lighting services at any of a group of lighting-enabled facilities in geographic region that is proximate to the portable electronic device. Various lighting facilities 803, 805, 811, 812 are represented on the map by location. Alternatively, available lighting facilities may be represented in a list or other format, optionally with identifying information describing the types of light-enabled locations that are available at the facility (e.g., basketball court, hockey rink, baseball field, soccer/lacrosse field, and the like). Each of the facilities shown in the user interface is light-enabled in that it will include a gateway controller and lighting devices as previously described in this document.

As shown in the flowchart of FIG. 9, a remote server may use geolocation data, such as that received from a GPS sensor of the portable electronic device or general location knowledge of the cellular network receiver to which the portable electronic device connects, to identify the location of the portable electronic device 901. The remote server then accesses a database of light-enabled facilities to identify those that are within a geographic distance range from the device's location 902. The database may store location data for each facility and identify those facilities whose associated location is within the range of the device's location. The range may be a predetermined range (such as a distance from the device's location), or the user interface may receive a user-defined range.

Optionally, database also may include scheduling information about each facility. If so, the server may retrieve lighting service schedules for each facility for a current time, and optionally for one or more future time periods from the database 903. The server may transmit data reflecting the lighting service schedules to the portable electronic device so that the portable electronic device may display the scheduling data on its user interface 904. For example, referring back to FIG. 8 facilities 803, 805 that are available at the current time may be displayed with a first icon and facilities 811, 812 that are in use and not currently available may be displayed with a second (different) icon. Other visually distinguishable availability indicators such as text, color, or pop-up may be used as well.

Returning to FIG. 9, the server may then receive a light operation request 905 that includes a selection of at least one of the displayed light-enabled facilities, a service time that corresponds to an available lighting service schedule, and a scene (which may simply be a default scene such as “turn all lights on”), and a future time period from the remote electronic device. The remote server may authenticate the request (using user account information as described in previous embodiments) 906 and transmit the scene initiation request and schedule to the gateway controller of the selected facility 907. The gateway controller of the selected facility will then operate the lights at that facility according to the schedule and scene using procedures such as that described above in (for example) FIG. 5. Optionally, the gateway controller may only initiate the scene if and after it detects that the portable electronic device, or another portable electronic device that is associated with the user's account in proximity of the light-enabled facility. The gateway controller may detect the portable electronic device's location by having paired with the portable electronic device (e.g., by short-range or near-filed communication as previously discussed), or by receiving data from the remote server indicating that the remote server has received geolocation data from the portable electronic device indicating that the device is proximate to the gateway controller.

FIG. 10 is a block diagram of hardware that may be included in any of the electronic devices described above, such as the gateway controller, the portable electronic device, the fixture controller, the remote server or the lighting device. A bus 1000 serves as an information highway interconnecting the other illustrated components of the hardware. The bus may be a physical connection between elements of the system, or a wired or wireless communication system via which various elements of the system share data. Processor 1005 is a processing device of the system performing calculations and logic operations required to execute a program. Processor 1005, alone or in conjunction with one or more of the other elements disclosed in FIG. 10, is an example of a processing device, computing device or processor as such terms are used within this disclosure. The processing device may be a physical processing device, a virtual device contained within another processing device, or a container included within a processing device. If the electronic device is a gateway controller, processor 1005 may be a component of the gateway controller. If the electronic device is a remote server, processor 1005 may be a component of a server on a cloud-computing network. If the electronic device is a lighting device, processor 1005 may be a component of a fixture controller if the fixture controller is an internal component of the lighting device, and the device would also include a power supply and optical radiation source as discussed above.

A memory device 1010 is a hardware element or segment of a hardware element on which programming instructions, data, or both may be stored. An optional display interface 1030 may permit information to be displayed on the display 1035 in audio, visual, graphic or alphanumeric format. Communication with external devices, such as a printing device, may occur using various communication interfaces 1040, such as a communication port, antenna, or near-field or short-range transceiver. A communication interface 1040 may be communicatively connected to a communication network, such as the Internet or an intranet.

The hardware may also include a user interface sensor 1045 which allows for receipt of data from input devices such as a keyboard or keypad 1050, or other input device 1055 such as a mouse, a touchpad, a touch screen, a remote control, a pointing device, a video input device and/or a microphone. Data also may be received from an image capturing device 1020 such as a digital camera or video camera. A positional sensor 1060 and/or motion sensor 1070 may be included to detect position and movement of the device. Examples of motion sensors 1070 include gyroscopes or accelerometers. Examples of positional sensors 1060 such as a global positioning system (GPS) sensor device that receives geolocation data from an external GPS network.

The features and functions described above, as well as alternatives, may be combined into many other different systems or applications. Various alternatives, modifications, variations or improvements may be made by those skilled in the art, each of which is also intended to be encompassed by the disclosed embodiments. 

The invention claimed is:
 1. A system for controlling one or more lighting devices, the system comprising: a processor; and a non-transitory memory device containing programming instructions for a lighting system control application that is configured to cause the processor to: receive geolocation data corresponding to an electronic device, identify one or more light-enabled facilities that are within a distance range of the electronic device, wherein each of the light-enabled facilities comprises a controller that is communicatively coupled to one or more lighting devices in a network of lighting devices, receive, from the electronic device, a light operation request comprising a selected one of the light-enabled facilities and a scene, and transmit, to the controller at the selected light-enabled facility, the light operation request to cause the controller to activate at least one lighting device at the selected light-enabled facility according to the scene.
 2. The system of claim 1, wherein: the light operation request further comprises a service time duration; and the lighting control application further comprises additional instructions to cause the processor to maintain the at least one lighting device in an activated state according to the scene until occurrence of an expiration event.
 3. The system of claim 2, wherein the expiration event comprises at least one of the following: occurrence of an off-time corresponding to the at least one lighting device or the selected light-enabled facility; or end of the service time duration.
 4. The system of claim 1, wherein the programming instructions to identify one or more light-enabled facilities comprise instructions to: use the geolocation data to identify a location of the electronic device; and access a database of light-enabled facilities and identify, from data in the database, one or more of the light-enabled facilities having a location that is within the distance range of the identified location of the electronic device.
 5. The system of claim 1, wherein the lighting control application further comprises additional instructions to cause the processor to, before receiving the light operation request: retrieve one or more lighting service schedules for the identified one or more light-enabled facilities; and transmit the one or more lighting service schedules to the electronic device.
 6. The system of claim 1, wherein the lighting control application further comprises additional instructions to cause the processor to: use user account information associated within the electronic device to authenticate the light operation request; and when transmitting the light authorization request to the controller, doing so only after authenticating the light operation request.
 7. The system of claim 1, further comprising the controller at the selected light-enabled facility, wherein the controller is configured to: detect whether the electronic device or another device that is associated with an account of a user of the electronic device is in proximity of the selected light-enabled facility; and only initiate the scene at the selected light-enabled facility of the electronic device or the other device is in proximity of the selected light-enabled facility.
 8. The system of claim 1, wherein the light operation request is configured to, when received by the controller, cause the controller to initiate or maintain the at least one lighting device in a first condition at a first time, and then switch the at least one lighting device to a second condition when the time duration expires.
 9. The system of claim 1, further comprising programming instructions for the lighting system control application to cause the processor to: receive from the electronic device, an identifier associated with the controller; and transmit to the electronic device a set of available scenes for the controller.
 10. The system of claim 1, further comprising programming instructions for the lighting system control application to cause the processor to determine whether the electronic device is authorized to cause the controller to implement the light operation request by: receiving a user credential from the electronic device or the controller; and verifying the user credential.
 11. The system of claim 1, further comprising programming instructions for the lighting system control application to cause the processor to determine whether the electronic device is authorized to cause the controller to implement the light operation request by: receiving a first account identifier from the controller; receiving a second account identifier from the electronic device; determining user credentials by comparing the first account identifier with the second account identifier; and verifying the user credential information.
 12. The system of claim 1, wherein the scene comprises a set of data corresponding to one or more optical characteristics of one or more lighting devices in the network, wherein the one or more optical characteristics comprise: a brightness or dimming level; color temperature; color; D_(uv); beam shape; or beam direction.
 13. The system of claim 1, wherein the programming instructions for the lighting system control application to cause the processor to receive the light operation request comprise programming instructions to: transmit, to the electronic device, identifying information for the one or more of the light-enabled facilities; and receive, from the electronic device, a selection of one of the light-enabled facilities to which to direct the light operation request, transmit, to the electronic device, the set of available scenes associated with one or more controllers of the selected local light-enabled facility.
 14. The system of claim 13, further comprising a database of data for a plurality of light-enabled facilities; and the programming instructions for the lighting system control application to cause the processor to identify the one or more of the light-enabled facilities that are within a distance range from the electronic device comprise instructions to access the database and extract from the database identification data for light-enabled facilities having location data that is within the distance range of the location of the electronic device.
 15. The system of claim 14, wherein: the database also includes a plurality of lighting service schedules for at least some of the light-enabled facilities in the database; and the non-transitory memory device further comprises additional programming instructions that are configured to cause the processor to, for at least some of the light-enabled facilities in the group: extract lighting service schedules from the database, based on the extracted lighting service schedules, identify lighting devices in the group having one or more available lighting service schedule times for which the lighting devices' light-enabled facility has not been reserved, identify a service time that corresponds to an available lighting service schedule times for the selected light-enabled facility, and update the database to indicate that the selected light-enabled facility has been reserved for the selected service time.
 16. The system of claim 15, wherein the programming instructions configured to cause the processor to identify the service time that corresponds to the available lighting service schedule times for the selected light-enabled facility comprise instructions to cause the processor to: transmit the lighting service schedules for at least some of the lighting devices in the group to the electronic device for output by a user interface of the electronic device, and receive, from the electronic device, the service time.
 17. A method for controlling lighting devices, the method comprising: receive geolocation data corresponding to an electronic device; identifying one or more light-enabled facilities that are within a distance range of the electronic device, wherein each of the light-enabled facilities comprises a controller that is communicatively coupled to one or more lighting devices in a network of lighting devices, receiving, from the electronic device, a light operation request comprising a selected one of the light-enabled facilities and a scene; and transmitting, to the controller at the selected light-enabled facility, the light operation request to cause the controller to activate at least one lighting device at the selected light-enabled facility according to the scene.
 18. The method of claim 17, wherein: the light operation request further comprises a service time duration; and the method further comprises, by the processor, maintaining the at least one lighting device in an activated state according to the scene until occurrence of an expiration event.
 19. The method of claim 18, wherein the expiration event comprises at least one of the following: occurrence of an off-time corresponding to the at least one lighting device or the selected light-enabled facility; or end of the service time duration.
 20. The method of claim 17, wherein identifying the one or more light-enabled facilities comprises: using the geolocation data to identify a location of the electronic device; and accessing a database of light-enabled facilities and identify, from data in the database, one or more of the light-enabled facilities having a location that is within the distance range of the identified location of the electronic device.
 21. The method of claim 17, further comprising, before receiving the light operation request: retrieving one or more lighting service schedules for the identified one or more light-enabled facilities; and transmitting the one or more lighting service schedules to the electronic device.
 22. The method of claim 17, further comprising: using user account information associated within the electronic device to authenticate the light operation request; and when transmitting the light authorization request to the controller, doing so only after authenticating the light operation request.
 23. The method of claim 17, further comprising, by a controller at the selected light-enabled facility: detecting whether the electronic device or another device that is associated with an account of a user of the electronic device is in proximity of the selected light-enabled facility; and only initiating the scene at the selected light-enabled facility of the electronic device or the other device is in proximity of the selected light-enabled facility.
 24. The method of claim 17, further comprising: receiving from the electronic device, an identifier associated with the controller; and transmitting to the electronic device a set of available scenes for the controller.
 25. The method of claim 17, further comprising determining whether the electronic device is authorized to cause the controller to implement the light operation request by: receiving a user credential from the electronic device or the controller; and verifying the user credential.
 26. The method of claim 17, further comprising determining whether the electronic device is authorized to cause the controller to implement the light operation request by: receiving a first account identifier from the controller; receiving a second account identifier from the electronic device; determining user credentials by comparing the first account identifier with the second account identifier; and verifying the user credential information.
 27. The method of claim 17, wherein receiving the light operation request comprises: transmitting, to the electronic device, identifying information for the one or more of the light-enabled facilities; and receiving, from the electronic device, a selection of one of the light-enabled facilities to which to direct the light operation request, transmitting, to the electronic device, the set of available scenes associated with one or more controllers of the selected local light-enabled facility.
 28. The method of claim 27, further comprising identifying one or more of the light-enabled facilities that are within a distance range from the electronic device by accessing a database and extracting from the database identification data for light-enabled facilities having location data that is within the distance range of the location of the electronic device, wherein the database comprises data for a plurality of light-enabled facilities.
 29. The method of claim 28, wherein: the database also includes a plurality of lighting service schedules for at least some of the light-enabled facilities in the database; and the method further comprises, for at least some of the light-enabled facilities in the group: extracting lighting service schedules from the database, based on the extracted lighting service schedules, identifying lighting devices in the group having one or more available lighting service schedule times for which the lighting devices' light-enabled facility has not been reserved, identifying a service time that corresponds to an available lighting service schedule times for the selected light-enabled facility, and updating the database to indicate that the selected light-enabled facility has been reserved for the selected service time. 